This chapter discusses the tasks associated with managing networks. Managing networks includes the creation, configuration, and management of virtual interfaces and network ports.
A virtual interface is associated with a network port and is assigned an IP address. A SpinServer port can be configured with one or more virtual interfaces with IP addresses and additional failover interfaces. Assigning failover interfaces is critical for creating a high-availability (HA) configuration.
In this chapter, you create a virtual interface and then create a virtual server on a a storage pool. For information on creating storage pools, see Chapter 11. After creating the virtual server, you bind the virtual interface to it.
Virtual interfaces must be created before virtual servers are created. After creating the virtual servers, you bind the virtual interfaces to the virtual servers.
To complete the network-management tasks, perform the following steps:
Create and configure a virtual interface.
Create a virtual server, which creates the root virtual file system.
Bind the virtual interface to the virtual server.
Associate a virtual interface with a network port.
The first step in managing virtual interfaces is to create and configure as many interfaces as the system needs. You name the virtual interfaces and associate them with an Ethernet port. When the interfaces are available to the system, there are many management tasks that are done occasionally, such as modifying the configuration of interfaces or deleting them.
You configure the interface as you create it. To configure a virtual interface, you need to obtain an IP address and netmask from your network administrator.
In the following table, enter the configuration information:
| IP address | |
| Netmask |
The if configuration new command creates an interface and identifies it by its host SpinServer, interface name, network port name, IP address, and netmask. The syntax of the command is as follows:
if configuration new -ssid spinserver -ifname interface_name -netportname network_port_name -ipaddress IP_address -netmask netmask
The following example creates a new interface named if0 on a SpinServer named Server1. The interface has a network port name of serv0, an IP address of 10.1.1.140, and a netmask of 255.255.255.0.
spinserver::> if configuration new -ssid Server1 -ifname if0 -netportname serv0 -ipaddress 10.1.1.140 -netmask 255.255.255.0
After creating virtual interfaces for the network, use the if status show command to display and review information about the virtual interfaces. The following information about the interfaces is displayed by the system:
SpinServer ID
Name
Network port
IP address
Netmask
Failover port
Cluster or server role in the network
The syntax of the command is as follows:
if status show [-ssid spinserver -ifname interface_name]
The following example displays information about all interfaces.
spinserver::> if status show
SpinServer Name Address Stat Active Active Virtual
ID Server Port
spsrv10 clus_if1 10.3.128.61 up spsrv10 clus1 false
spsrv10 clus_if0 10.3.128.60 up spsrv10 clus0 false
spsrv10 mgmt_if0 10.3.2.115 up spsrv10 mgmt0 false
The following example displays information about the interface named rData0 on the SpinServer named spsrv10:
spinserver::> if status show -ssid spsrv10 -ifname rData0 SpinServer ID spsrv10 Name rData0 Port serv1 Address 10.5.15.58 Status up Role Server Active Server spsrv10 Active Port serv1 Virtual true
To migrate a virtual interface from one port to another, use the if status migratevif command. This command is useful when you are working with a high-availability (HA) configuration and you need to move a virtual interface from a failed primary server to a secondary server. The syntax of the command follows.
if status migratevif -ssid spinserver -ifname virtual_interface_name -destssid destination_spinserver -destport destination_port
The following example moves a virtual interface named vif0 on SpinServer Server1 to port serv0 on SpinServer Server2.
spinserver::> if status migratevif -ssid Server1 -ifname vif0 -destssid Server2 -destport serv0
After creating virtual interfaces for the network, use the if configuration show command to display and review the configuration information for the virtual interfaces. The following information about the interfaces is displayed by the system:
SpinServer ID
Name
Network port
IP address
Netmask
Failover port
The syntax of the command is as follows:
if configuration show -ssid spinserver -ifname interface_name
The following example displays information about all the configuration of all interfaces.
spinserver::> if configuration show
SpinServer ID Name Port IP Address Netmask Failover
Port
spsrv10 rData0 serv1 10.5.15.58 255.255.0.0
spsrv10 Data0 serv0 10.5.10.58 255.255.0.0
spsrv10 rData1 serv0 10.5.15.162 255.255.0.0
spsrv10 rData2 serv1 10.5.15.161 255.255.0.0
spsrv10 rData3 serv0 10.5.15.160 255.255.0.0
spsrv10 rData4 serv1 10.5.15.157 255.255.0.0
spsrv10 clus_if0 clus0 10.3.128.20 255.255.128.0
spsrv10 rData5 serv0 10.5.15.158 255.255.0.0
spsrv10 clus_if1 clus1 10.3.128.28 255.255.128.0
The following example identifies an interface named if0 on a SpinServer named spsrv10 and displays its configuration information.
spinserver::> if configuration show -ssid spsrv10 -ifname if0 SpinServer ID spsrv10 Name rData0 Port serv1 IP Address 10.5.15.58 Netmask 255.255.0.0 Failover Port VIF ID 6 Role Server
If a virtual interface is not needed or becomes obsolete, you can remove it from the network by using the if configuration delete command. The command has the following syntax:
if configuration delete -ssid spinserver -ifname interface_name
The following example deletes a virtual interface named if0 on a SpinServer named spsrv10.
spinserver::> if configuration delete -ssid spsrv10 -ifname if0
The configuration of a virtual interface can be modified when the virtual interface is online. The configuration change takes effect when the interface is restarted (that is, after making the change, you must take the interface offline, then bring it back online). Adding or removing a virtual interface route takes effect immediately.
The if configuration offline command identifies an interface by its SpinServer ID and interface name and takes the interface offline. The command has the following syntax:
if configuration offline -ssid spinserver -ifname interface_name
The following example takes an interface named if0 on a SpinServer named spsrv10 offline.
spinserver::> if configuration offline -ssid spsrv10 -ifname if0
After making changes in the configuration of a virtual interface, use the if configuration online command to bring the interface back online. The command has the following syntax:
if configuration online -ssid spinserver -ifname interface_name
The following example brings an interface named if0 online on a SpinServer named spsrv10.
spinserver::> if configuration online -ssid spsrv10 -ifname if0
After virtual interfaces are created, changes to the configuration of the interfaces are sometimes necessary. Use the if configuration modify command to modify configuration information for a virtual interface.
The if configuration modify command identifies a given interface by its SpinServer ID and interface name and enables you to modify the IP address and netmask of an interface. Changing the netmask changes the virtual interface's subnet assignment.
The command has the following syntax:
if configuration modify -ssid spinserver -ifname interface_name -ipaddress IP_address -netmask netmask
The following example changes the IP address to 10.1.1.130 of an interface named if0 on a SpinServer named spsrv10. The interface has the netmask 255.255.255.0.
spinserver::> if configuration modify -ssid spsrv10 -ifname if0 -ipaddress 10.1.1.130 -netmask 255.255.255.0
After a failover, you can revert virtual interfaces automatically to their home ports by using the if status revertvifs command. The command takes no parameters; issuing the command reverts all virtual interfaces to their home ports, as in the following example.
spinserver::> if status revertvifs
Failover is an important fault-tolerance function of systems that rely on constant accessibility, including high-availability (HA) configurations. Failover automatically and transparently redirects user requests from the failed or downed network to a backup network that takes over the operations of the primary network. Each virtual interface can have multiple failover ports. A virtual interface (IP address) migrates to the failover port in the event of a failure.
A failover port can be purely a standby port, or it can be a fully configured port with active virtual interfaces. Adding a failover port provides the system with a standby interface that automatically switches to a standby SpinServer or network if the primary network fails or is temporarily shut down for servicing. A failover port can be a port on either the local node or a remote node.
When a virtual interface is bound to a network port, that port is marked as the interface's primary port and serves as the default failover port in the unlikely event of multiple failures. If the virtual interface fails over and a failure occurs on the failover port, the interface can then be redirected to the original port.
Cluster link failover is enabled automatically, without explicit configuration. The cluster link fails over to the peer cluster link on the same node if the peer link is available.
To assign a failover port to the interface, use the if configuration addfailport command. The command has the following syntax:
if configuration addfailport -ssid spinserver -ifname interface_name -ssidto failover_spinserver -netportnameto network_failover_port_name
The following example identifies an interface named if0 on a SpinServer named spsrv10 and adds a server port named serv2 on a SpinServer named spsrv12 as a failover port.
spinserver::> if configuration addfailport -ssid spsrv10 -ifname if0 -ssidto spsrv12 -netportnameto serv2
To remove a failover port from the interface, use the if configuration removefailport command. The syntax of the command follows.
if configuration removefailport -ssid spinserver -ifname interface_name -ssidfrom failover_spinserver -netportnamefrom network_failover_port_name
The following example removes a failover port named if2 on a SpinServer named spsrv12 from an interface named if0 on a SpinServer named spsrv10.
spinserver::> if configuration removefailport -ssid spsrv10 -ifname if0 -ssidfrom spsrv12 -netportnamefrom if2
Ports represent physical Ethernet connections. The Ethernet ports are identified in Table 5-1.
The management port on a SpinServer is the connection to the management interface. The management port is automatically configured when the SpinServer is started.
A server port can be configured with one or more virtual interfaces with IP addresses. Virtual interfaces are named by the user and associated with an Ethernet port.
Assign an IP address to a virtual interface by using the if configuration new command. The syntax of the command follows.
if configuration new -ssid spinserver -ifname interface_name -netportname network_port_name -ipaddress IP_address -netmask netmask
The following example configures a virtual interface named if0 on the server port named serv0 (the first of two server ports) and the SpinServer named Server1. The port is given the IP address 10.1.1.139 and the netmask 255.255.255.0.
spinserver::> if configuration new -ssid Server1 -ifname if0 -ipaddress 10.1.1.139 -netmask 255.255.255.0 -netportname serv0
The following example configures a virtual interface named if0 on the server port named serv1 (the second of two server ports) and the SpinServer named Server1. The port is given the IP address 10.1.1.140 and the netmask 255.255.255.0.
spinserver::> if configuration new -ssid Server1 -ifname if0 -ipaddress 10.1.1.140 -netmask 255.255.255.0 -netportname serv1
The first cluster port is configured when you use either the spinserver createcluster command or the spinserver joincluster command.
Note: To assure that all system components work together properly, the cluster port must be configured even if only a single SpinServer is being installed. Even if you intend to use only one of the cluster ports, it is strongly recommended that you configure both cluster ports at initial installation of the software.
If you did not configure the second cluster port at the time you initially installed the software, use the if configuration new command to configure the second cluster port.
After configuration is completed, the SpinServer can recognize disk drives and RAID sets. A cluster port can be configured with only one IP address. With the cluster port configured, accessing one SpinServer also provides you with access to files that reside on disks that are attached to another SpinServer. You can perform administrative tasks with RAID sets and virtual file systems on both SpinServers.
The following example configures a virtual interface named if0 on the second cluster port (clus1) on a SpinServer named Server1. The port is given the IP address 10.1.1.145 and the netmask 255.255.255.0.
spinserver::> if configuration new -ssid Server1 -ifname if0 -ipaddress 10.1.1.145 -netmask 255.255.255.0 -netportname clus1
You can add a static route to a virtual interface to make network traffic move more efficiently. Use the if configuration addroute command to add a route to a virtual interface. The command has the following syntax:
if configuration addroute -ssid spinserver -ifname interface_name -destaddr destination_IP_address -destmask destination_mask -nexthop next_hop_IP_address
The following example adds a route to a virtual interface named vif0 on a SpinServer named Server1. The route has a destination IP address of 192.40.5.1, a destination mask of 255.255.255.0, and a next-hop IP address of 192.40.6.1.
spinserver::> if configuration addroute -ssid Server1 -ifname vif0 -destaddr 192.40.5.1 -destmask 255.255.255.0 -nexthop 192.40.6.1
Use the if routes delete command to delete a static route from a virtual interface. The command has the following syntax:
if routes delete -ssid spinserver -ifname interface_name -destaddr destination_IP_address -destmask destination_mask -nexthop next_hop_IP_address
The following example deletes a route from a virtual interface named vif0 on a SpinServer named Server1. The route has a destination IP address of 192.40.5.1, a destination mask of 255.255.255.0, and a next-hop IP address of 192.40.6.1.
spinserver::> if routes delete -ssid Server1 -ifname vif0 -destaddr 192.40.5.1 -destmask 255.255.255.0 -nexthop 192.40.6.1
Use the if routes show command to display information about routes on one or more virtual interfaces. The command has the following syntax:
if routes show [-ssid spinserver -ifname interface_name]
The following example displays route information about a virtual interface named vif0 on a SpinServer named Server1:
spinserver::> if routes show -ssid Server1 -ifname vif0
SpinServer Name Destination IP Destination Next Hop
ID Address Netmask
Server1 vif0 192.40.5.1 255.255.255.0 192.40.6.1
To display configuration information about all ports or information about one port, use the ports show command. To display information about one network port, use the command with the -ssid and -netportname parameters. To display configuration information about a list of ports on the network, use no parameters. The command displays the following information:
SpinServer ID
Port name
Maximum Transmission Unit (MTU)
Media access control (MAC) address
Online status (up or down)
Link status
Whether autonegotiation is enabled (true or false)
Whether full duplexing is enabled (true or false)
Port speed
The syntax of the command follows.
ports show [-ssid spinserver -netportname network_port_name]
The following example displays configuration information about all network ports in the cluster.
spinserver::> ports show
SpinServer ID Name MTU Status Auto Full Speed
Negoti Duplex
p416 clus0 1500 up true true 1000
p416 clus1 1500 up true true 1000
p416 mgmt0 1500 up
p416 serv1 1500 up true true 1000
p416 serv0 1500 up true true 1000
p48 mgmt0 1500 up
p48 clus0 1500 up true true 1000
p48 serv1 1500 up true true 1000
p48 clus1 1500 up true true 1000
p48 serv0 1500 up true true 1000
The following example displays configuration information about the network port named serv1 on the SpinServer named Server1.
spinserver::> ports show -ssid Server1 -netportname serv1 SpinServer ID Server1 Name serv1 MTU 1500 MAC Address 00:04:76:F8:D2:FC Status up Link Status link Auto Negotiate true Full Duplex true Speed 1000
To make an IP address unavailable to clients while doing network maintenance tasks, use the ports down command to take the port down before changes are made.
Note: Using the ports down command takes down all virtual interfaces assigned to the port.
To take down a port from the network, use the ports down command. The syntax of the command follows.
ports down -ssid spinserver -netportname network_port_name
The following example takes down the port named serv1 on the SpinServer named Server1.
spinserver::> ports down -ssid Server1 -netportname serv1
To bring up a port for the network, use the ports up command. The syntax of the command follows.
ports up -ssid spinserver -netportname network_port_name
The following example brings up the port named serv1 on the SpinServer named Server1.
spinserver::> ports up -ssid Server1 -netportname serv1
To modify the settings for a network port, use the ports modify command. An MTU is the largest physical packet size, measured in bytes, that a network can transmit. Any messages larger than the MTU are divided into smaller packets before being sent.
The ports modify command modifies the maximum transmission unit (MTU) size, autonegotiation setting, full-duplexing setting, and port speed of a network port. The changes takes effect immediately, without the port needing to be restarted. By default, the server ports have an MTU value of 1500 bytes, an autonegotiation setting of true, a full-duplexing setting of true, and a speed of 1000. The syntax of the command follows.
ports modify -ssid spinserver -netportname network_port_name -mtu maximum_transmission_unit -autonegotiate {true | false} -fullduplex {true | false} -speed speed
The following example identifies a port named serv1 on a server named Server1 and modifies the maximum transmission unit size to 9000 bytes, the autonegotiation value to true, the full duplexing value to false, and the port speed to 1000.
spinserver::> ports modify -ssid Server1 -netportname serv1 -mtu 9000 -autonegotiate true -fullduplex false -speed 1000
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.